Population selection framework, systems and methods

ABSTRACT

Tools providing a flexible selection framework for automated processes. The framework can allow end-users to define their own selection criteria to select a data population to be processed (for example, by a business application). Hence, the tools provide enhanced control over what data is provided to which process. Some such tools employ metadata to define what information the client process needs, how the results will be returned to the client process, and/or what selection tools should be available to select data for the client process, as well as the available data selection tools, which can include both tools provided with a business application as well as third-party and/or user supplied selection tools. The framework might also provide an application programming interface that ensures consistent communication between the population selection engine and the selection tools themselves.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of co-pending U.S. patentapplication Ser. No. 12/042,713, filed Mar. 5, 2008 and entitled“Population Selection Framework, Systems and Methods, which claims thebenefit, under 35 U.S.C. §119(e), of provisional U.S. Pat. App. No.60/975,139, filed Sep. 25, 2007 by Michael Kennedy et al. and entitled“Population Selection Framework, Systems and Methods,” and provisionalU.S. Pat. App. No. 61/013,841, filed Dec. 14, 2007 by Marina Krasner etal. and entitled “Population Selection and Update Framework, Systems andMethods.” The entire disclosure of each of these provisionalapplications is hereby incorporated herein by reference for allpurposes.

This application is also related to U.S. patent application Ser. No.12/042,738, (attorney docket no. 021756-046900US) filed on Mar. 5, 2008by Michael Kennedy et al. and entitled “Population Update Framework,Systems and Methods,” the entire disclosure of which is incorporatedherein by reference for all purposes.

COPYRIGHT STATEMENT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

The present invention relates, in general, to business applications andmore particularly, to tools for selecting data to be processed bybusiness applications and/or for updating data in business objects.

BACKGROUND

Many businesses, educational institutions, and other organizations usesoftware applications (and/or suites of such applications) to organizetheir business affairs, track business performance, manage employee data(and/or student data, etc.) and/or the like. Such applications (referredto herein as “business applications”) are often quite complex, relyingon numerous database tables to store and manage data for virtually everyaspect of an organization's business. Merely by way of example, businessapplications can include supply chain management (“SCM”) applicationsthat manage raw materials, work-in-process and/or finished products,coordinate with suppliers, and/or the like; customer relationsmanagement (“CRM”) applications that are used to track, store and/ormanage customer information; financial applications that track and/oranalyze the financial performance of the organization; human resourcesapplications that provide management of the human resources functions ofthe organization; and/or the like. In some cases, these businessapplications are standalone applications; in other cases, a singlebusiness application (and/or suite of applications) might provide someor all such functionality. One type of business application is referredto enterprise resource planning (“ERP”) software. Examples of businessapplications include, without limitation, JD Edwards EnterpriseOne,PeopleSoft Enterprise applications (including, for example, PeopleSoftEnterprise Student Administration), and the Oracle eBusiness Suite, allavailable from Oracle Corporation.

One task commonly required of a business application is to process datain one or more data objects (which can include, but is not necessarilylimited to, data stored in one or more tables of a database managed by arelational database management system (“RDBMS”) and maintained by thebusiness application, data stored in an object-oriented data structureoutside of a database, data stored in a flat tile, spreadsheet, etc.,and/or the like). Processing data can include many tasks, includingwithout limitation, adding new data to the data object (e.g. adding newrecords to a table, adding data to an existing record, etc.) from a datasource outside the data object, and/or updating existing data in a dataobject (e.g., modifying properties or parameters of an object-orientedbusiness object, modifying fields in a database record/table, etc.).Business applications often provide automated (or semi-automated)processes for performing these tasks. Oftentimes, not all available datashould be processed, however; instead, the business application'sprocess(es) should be applied selectively, so as to only process theappropriate data.

In the past, the criteria to select a data population to process werepredefined and delivered bundled with business application processes.This solution left end users with little or no flexibility on how torefine the selection criteria. Often, consulting services or internalengineering resources were employed to extend or modify the deliveredprocesses to fit the customers' ever changing criteria requirements.Modifying the large number of automated processes and maintaining theseenhancements proved costly to customers.

Similarly, tools for updating data in such business objects haveexhibited shortcomings. Merely by way of example, in many cases, dataobjects are not directly-accessible for modification by end users, butinstead require access via an application programming interface (“API”).While there may exist tools for modifying a data object via this API,such tools are often inflexible, providing users with insufficientability to effect changes in the data objects. Moreover, while usersmay, in some instances, have the ability to update data in a businessobject directly, in many such instances, indiscriminate modification ofa data object (such as modification of a key field in a databaserecord), can produce undesirable and/or catastrophic results rangingfrom reduced performance to loss of data integrity, among otherproblems.

Accordingly, there is a need for more flexible tools to select a datapopulation for processing by a business application (or any other typeof application). There is a further need for tools that can provide auser with flexibility to update data in data objects while stillproviding sufficient controls to prevent modifications that mayadversely impact the updated business objects.

BRIEF SUMMARY

In an aspect, some embodiments of the invention provide a flexibleselection framework for automated processes. The framework allowsend-users to define their own selection criteria to select a datapopulation to be processed (for example, by a business application). Inone novel aspect, the population selection features of certainembodiments can be integrated with the interface for a businessapplication process, providing a one step action to select and providethe appropriate data for processing by the business application.

In another novel aspect of some embodiments, the definition of theselection criteria for a process is not hard coded inside the process.This provides enhanced control over what data is provided to whichprocess. In some cases, the user even has the option preview theselected data population for the process, in order to confirm theaccuracy of the selection criteria before processing the selected data.

Tools provided by some embodiments employ metadata to define whatinformation the client process needs, how the results will be returnedto the client process, and/or what selection tools should be availableto select data for the client process. In another aspect of someembodiments, metadata to define the available selection tools, which caninclude both tools provided with a business application as well asthird-party and/or user supplied selection tools. Hence, particularembodiments of the invention easily can be configured to support newbusiness application processes and/or selection tools without requiringextensive modification of the underlying population selection frameworkor its implementing software. In an aspect, this flexibility mayprovided, inter alia, by an application programming interface (of whichone example is an object oriented interface definition), that ensuresconsistent communication between the population selection engine and theselection tools themselves.

Another set of embodiments provides a flexible update framework andutility for automated processes. In an aspect, an update utility canprovide an interface to allow a user to employ desired selection tools(including without limitation, the selection tools of variousembodiments) to select a data population to be updated. In anotheraspect, the update framework of these embodiments can also provide aflexible interface that can employ any of a variety of update tools toupdate the desired data population (including, without limitation,database procedures, such as SQL functions; object-oriented accessmethods, specialized applications, and/or the like).

The update framework, in some embodiments, employs metadata to definewhat information a data update tool needs, and/or the format in whichthe data should be provided to the tool. Metadata may also be usedidentity available update tools for the selected data objects; suchtools can include both tools provided with a business application and/ordatabase, as well as third-party and/or user supplied update tools.Hence, certain embodiments of the invention easily can be configured tosupport new update tools without requiring extensive modification of theunderlying population update framework or its implementing software. Inan aspect, this flexibility may provided, inter alia, by an adapterinterface (of which one example is an object oriented interfacedefinition), that ensures consistent communication between thepopulation update engine and the respective interfaces (e.g., APIs) ofthe update tools themselves.

In specific embodiments, the update framework may also employ metadatato define, for particular types of data objects, which data elements(e.g., fields, properties, parameters, etc.) an update tool is allowedto modify, since the framework anticipates the integration of the updateutility of certain embodiments with update tools that can be used tomodify data objects indiscriminately. Hence, in different aspects, theupdate utility of various embodiments can not only provide a consistentinterface between desired population selection tools and desired dataupdate tools (including tools that are not designed to beinteroperable), but can also provide controls that such existing toolslack, thereby preventing unintentional damage of data objects byprohibiting modification of protected data elements.

The tools provided by various embodiments of the invention include,without limitation, methods, systems, and/or software products. Mainlyby way of example, a method might comprise one or more procedures, anyor all of which are executed by a computer system. Correspondingly, anembodiment might comprise a computer system configured with instructionsto perform one or more procedures in accordance with methods provided byother embodiments. Similarly, a computer program might comprise a set ofinstructions that are executable by one or more computer systems (and/orone or more processors therein) to perform such operations. In manycases, such software programs are encoded on physical and/or tangiblecomputer readable media (such as, merely by way of example, opticalmedia, magnetic media, and/or the like).

Merely by way of example, one set of embodiments provides a softwareframework for selecting set of data population to be processed by abusiness application. The framework may be implemented by computerprogram (i.e., a set of instructions) encoded on a computer readablemedium. The computer program might be executable by a computer system toimplement the framework. In a set of embodiments, the framework mightcomprise a population selection engine configured to provide a set ofdata, selected from a data source, to a business application forprocessing. The framework might also comprise one or more sets ofselection tool metadata, including a first set of selection toolmetadata comprising information about first a selection tool that can beused by the population selection engine for selecting data to provide tothe business application, and/or one or more sets of selection contextmetadata, including a first set of selection context metadata comprisinginformation about first a business application process implemented bythe business application to process the set of data. In addition and/oralternatively, the framework might include an API for providingcommunication between the population selection engine and the one ormore selection tools.

Another set of embodiments provides methods of processing data and/or ofselecting data to be processed. An exemplary method of selecting data tobe processed with a business application comprises providing apopulation selection framework (such as that described above, forinstance). The exemplary method, in an embodiment, further comprisesproviding a user interface from a computer system and/or receiving via,the user interface, a first set of selection tool metadata for a firstselection tool that can be used by the population selection engine forselecting data to provide to the business application and/or a first setof selection context metadata comprising information about first abusiness application process implemented by the business application toprocess the data. In some embodiments, the method further comprisesconfiguring the population selection engine based on the first set ofselection tool metadata and the first set of selection context metadata,and/or providing, e.g., via the user interface, a display to allow theuser to select the first selection tool (for selecting a set of datafrom a data source), and the first business application process (forprocessing the selected set of data).

Another exemplary method of selecting data for processing with abusiness application comprises providing, at a computer system, apopulation selection engine for selecting data to be processed with abusiness application, and/or providing, from the computer system, a userinterface for a user to interact with the population selection engine.In some cases, the method further comprises, receiving, via the userinterface, identification of a first selection tool to be used to selectdata to be processed with the business application and/or identifying adata source comprising the data to be processed with the businessapplication. The method might also include invoking, from the populationselection engine, a selection tool to select data to be processed withthe business application, receiving, from the selection tool, aselection of one or more sets of data to be processed with the businessapplication, and/or providing the selected one or more sets of data tothe business application for processing.

Other embodiments provide a method of processing data with a businessapplication. One such method comprises providing, at a computer system,a population selection engine for selecting data to be processed withthe business application, and/or maintaining, at the computer system, aset of metadata for each of one or more selection tools. The set ofmetadata in an aspect, might define a relationship between each of theone or more selection tools and the population selection engine. Themethod can further include providing, from the computer system, a userinterface for a user to interact with the population selection engine,receiving, via the user interface, identification of a first selectiontool to be used to select data to be processed with the businessapplication, and/or identifying a data source comprising the data to beprocessed with the business application. In some cases, the method alsoincludes invoking, based on at least a portion of the set of metadata,the first selection tool from the population selection engine to selectdata to be processed with the business application, receiving, from theselection tool, a selection of one or more sets of data to be processedwith the business application. Optionally, the method can includeprocessing each of the one or more sets of data with the businessapplication and/or displaying an indication of a result of theprocessing.

Another exemplary embodiment provides methods of updating data in one ormore business objects. One such method comprises providing, at acomputer system, a population update engine for updating data inbusiness objects, and/or maintaining, at the computer system, a firstset of update context metadata for one or more update tools, the set ofupdate context metadata defining a relationship between the one or moreupdate tools and the and the population update engine. In some cases,the method might also comprise maintaining, at the computer system, asecond set of update context metadata for a one or more datapopulations, each of the data populations comprising a plurality ofbusiness objects, the second set of update context metadata comprisinginformation about a structure of business objects in each of the datapopulations.

The method, in an aspect, may also include providing, from the computersystem, a user interface for a user to interact with the populationupdate engine, and/or receiving, at the population update engine and viathe user interface, a first user input. Based, in some cases on thefirst user input, a data population to be updated can be identified; thedata population, in an aspect, comprises one or more business objects.The method, then, may include identifying an update tool for updatingthe selected data population and/or determining (e.g., based on updatecontext metadata for the identified data population) one or more dataelements that can be modified by the update tool. These data elementsmay be displayed for the user, via the user interface, and the methodcan include receiving, via the user interface, a second user inputcomprising a selection of one or more data elements to be updated and anupdate value for each of the one or more data elements.

In some cases, the method further comprises invoking the identifiedupdate tool to update the identified data population with the updatevalue for each of the one or more data elements and/or providing anupdate status indicating a result of invoking the identified updatetool.

Another embodiment provides a computer readable medium having encodedthereon a set of instructions executable by a computer to implement aframework for updating data in one or more business objects. In anaspect, the framework comprises a population update engine configured toreceive a data population comprising one or more business objects fromone or more data sources, and provide the data population to an updatetool appropriate for updating one or more data elements. In anotheraspect, the framework comprises an adapter interface configured tointeract with one or more of a plurality of update tools (including,without limitation, the update tool appropriate for the selected set ofdata) to update the one or more data elements in each of the businessobjects. In a third aspect, the framework comprises one or more sets ofupdate context metadata, including a first set of update contextmetadata defining a relationship between the population update engineand each of the plurality of update tools. Optionally, the frameworkmight comprise a user interface for receiving, from a user, inputpertaining to the set of data to be updated;

Yet another set of embodiments provides computer systems. An exemplarycomputer system might comprise one or more processors (which might beincorporated within one or more computers, such as a server computerand/or a client computer) and a computer readable medium having encodedthereon instructions executable by the one or more processors toimplement the software framework provided by various embodiments and/orthe perform one or more operations in accordance with methods of variousembodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of some embodimentsof the present invention may be realized by reference to the remainingportions of the specification and the drawings wherein like referencenumerals are used throughout the several drawings to refer to similarcomponents. In some instances, a sublabel is associated with a referencenumeral to denote one of multiple similar components. When reference ismade to a reference numeral without specification to an existingsublabel, it is intended to refer to all such multiple similarcomponents.

FIGS. 1A and 1B are block diagrams illustrating a software framework forselecting data to be processed by a business application, in accordancewith various embodiments of the invention.

FIG. 2 is a process flow diagram illustrating a method of configuring apopulation selection engine, in accordance with various embodiments ofthe invention.

FIGS. 3A, 3B and 3C are exemplary screen displays illustratinginterfaces for configuring a population selection engine, in accordancewith various embodiments of the invention.

FIG. 4 is a process flow diagram illustrating a method of processingdata in a business application, in accordance with various embodimentsof the invention.

FIG. 5 is an exemplary screen display illustrating a user interface forselection a set of data to be processed by a business application, inaccordance with various embodiments of the invention.

FIG. 6 is a generalized schematic diagram illustrating a computersystem, in accordance with various embodiments of the invention.

FIG. 7 is a block diagram illustrating a networked system of computers,which can be used in accordance with various embodiments of theinvention.

FIGS. 8A, 8B and 8C are block diagrams illustrating a software frameworkfor updating data to be processed by a business application, inaccordance with various embodiments of the invention.

FIG. 9 is a process flow diagram illustrating a method of configuring apopulation update engine, in accordance with various embodiments of theinvention.

FIG. 10 is and exemplary screen display illustrating an interface forconfiguring a population update engine, in accordance with variousembodiments of the invention.

FIG. 11 is a process flow diagram illustrating a method of updating datain a business application, in accordance with various embodiments of theinvention.

FIG. 12 is an exemplary screen display illustrating a user interface forupdating a set of data to be processed by a business application, inaccordance with various embodiments of the invention.

DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS

While various aspects of certain embodiments of the invention have beensummarized above, the following detailed description illustrates a fewexemplary embodiments in further detail to enable one of skill in theart to practice the invention. In the following description, for thepurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of various embodiments thepresent invention. It will be apparent, however, to one skilled in theart that other embodiments of the present invention may be practicedwithout some of these specific details. In other instances, well-knownstructures and devices are shown in block diagram form. Severalembodiments of the invention are described below, and while variousfeatures are ascribed to different embodiments, it should be appreciatedthat the features described with respect to one embodiment may beincorporated with another embodiments as well. By the same token,however, no single feature or features of any described embodimentshould be considered essential to the invention, as other embodiments ofthe invention may omit such features.

In an aspect, some embodiments of the invention facilitate theprocessing of data with a business application. In particular, certainembodiments can be used to select, for processing, a data populationfrom a larger set of data in a data source, and feed the selected datato a process in a business application (or any other suitableapplication). Beneficially, the population selection techniques ofvarious embodiments can allow an application developer and/or user anenhanced degree of flexibility in determining how to select data for aparticular process.

As noted above, there are a wide variety of business applicationsavailable, and particular embodiments of the invention can be used byany such application, as well as other types of software that requiredata processing and/or selection. The term “business applicationprocess” (sometimes referred to herein as a “client process” of thepopulation selection engine, or merely as a “process”), as used herein,means any type of process, operation, or series of operations performedon a data population by such an application. A business applicationprocess might, for example, be used to import data into a businessapplication (and/or a database used by the business application), tomodify or update data already in such a database, to provide decisionsupport functions, to generate reports, and/or the like. Virtually anyfunction of a business application can be implemented as a businessapplication process.

Many business applications are designed to process data in a variety offormats, including without limitation, data from a flat file,spreadsheet, etc. (which might need to be imported into the businessapplication and/or a database used by the business application), dataalready in a database (which might need to be modified by the process,etc.), and/or a variety of other types of information. Certainembodiments can allow the user to select the appropriate data selectiontool for the type of data to be processed and/or for the process to beused. In some embodiments, one or more pre-configured data selectiontools may be provided with the business application, while in otherembodiments, the user (and/or a developer) can be given the option tointerface with third-party selection tools that may be more appropriatefor the user's specific requirements.

Consider, for example, a business application that is configured tomanage data about an educational institution, such as a university. Thebusiness application might be configured to store (e.g., in a relationaldatabase) data about various students, employees, etc. If anadministrator desires to add a new group of students to the database,the administrator might have a spreadsheet with biographical informationabout the new students—for instance, each row in the spreadsheet mightrepresent a data record for a particular spreadsheet, and each column inthe spreadsheet might represent a particular data element (name,address, SAT score, undergraduate GPA, etc.) for each student. Theadministrator, then, can use a spreadsheet-specific selection tool toselect the appropriate students from the spreadsheet (based, perhaps, onthe value of a particular data field in each student record in thespreadsheet) to be processed by the business application and insertedinto the database.

In this example, the administrator might also want to update severalstudent records already in the database (for example, to indicate thatcertain students have qualified for financial aid). In that case, theadministrator might need to use a selection tool that is configured toselect data from a table in the database (using, for example, structuredquery language (“SQL”) statements to select the appropriate populationof students. The selected student records can then be processed toupdate those records to indicate that financial aid has been awarded,using a standard process within the business application.

As this example illustrates, some embodiments of the invention can beused to provide a user with a variety of data selection toolsappropriate to the type(s) of data being selected, while still providinga consistent interface with defined processes of a business application.The user is not necessarily limited to a pre-configured data selectiontool that is hard coded into the business application. Instead, tools inaccordance with certain embodiments of the invention provide the userwith flexibility to use one of several defined data selection tools(and, in some cases, even to interface with additional selection toolswritten by the user or a third party) to select data to be processed,allowing the user to choose the best selection tool for the type of datato be selected.

I. Population Selection Framework

In an aspect, one set of embodiments provides this flexibility through arobust software framework for selecting a data population to beprocessed. FIGS. 1A and 1B illustrate a population selection framework100 in accordance with some embodiments of the invention. In theillustrated embodiment, the framework 100 comprises a populationselection engine 105 and one or more selection tools 110. As usedherein, the term “population selection engine” is used to refer to anysoftware tool, application and/or component that can be used to selectdata for processing by a business application, and/or optionally, toformat or convert the data for use by the process. In this way, thepopulation selection engine 105 can serve as an intermediary between apredefined process in a business application and a set of data thatmight otherwise be unusable by the process.

In an aspect, the population selection engine 105 can use a variety ofselection tools 110 to interface with a variety of data sources toselect and/or obtain the data for processing. As used herein, the term“selection tool” means any type of software tool, application and/orcomponent that is configured to access a data source, select data fromthe data source, and/or provide the data to the population selectionengine 105. Examples of selection tools include, without limitation, aSQL query tool (which might be provided by the business applicationand/or the RDBMS for the database) that can be used to query a databaseto select data sets, a spreadsheet selection tool that can be used tointerface with a spreadsheet (and/or a spreadsheet application) toselect data from the spreadsheet, a spreadsheet application itself, astandalone data selection application such as a flat file selection toolthat can be used to parse a text (or other type of) file to select data,an equation engine that can be used to allow a user to develop a formulafor selecting data sets from a variety of data sources (includingdatabase tables, etc.), and the like.

Hence, the population selection engine 105 is configured to interfaceboth with a selection tool 110 and with a client process 115 in abusiness application 175, which may be used to update a database 120that is used by the business application 175. The framework 100 mightalso comprise a user interface (which might be a graphical userinterface provided by the business application 175, by the selectiontool 105 itself, etc.) In some cases, the user interface 145 is providedas a web interface (that is, a set of one or more web pages served by aweb server and/or application server and displayed by a web browser on aclient computer, as described in more detail below).

The operation of the population selection engine 105 is described infurther detail below; in general, however, the population selectionengine 105 invokes a selection tool 110 based, in some cases, on userinput received via the user interface 145. The selection tool 110 isconfigured to select one or more sets of data (referred to herein as adata “population”) from a data source 140 and return that datapopulation to the population selection engine 105. The populationselection engine 105, then, provides the selection results (whichinclude the selected data sets, perhaps after conversion and/orformatting, as described in further detail below), to the client process115 in the business application 175, which processes the selected datasets, optionally updating a database 120 used by the businessapplication.

The data source 140 can be any of a variety of data sources, includingwithout limitation a database and/or database table (which, in somecases, might be the database 120 used by the business application 175),a spreadsheet, a flat file, a data store for a separate application(such as an email application, etc.), and/or any of a variety of datasources. In fact, one benefit of certain embodiments is the wide rangesof different data sources that can be used to obtain data for processingby the business application 175—using an appropriate selection tool 110,virtually any type of data source may be supported.

Although only one selection tool 110 and client process 115 are depictedin FIGS. 1A and 1B, a single population selection engine 105 can supportany number of either of these components. It is often the case, however,the selection engine 105 needs to be configured to operate properly witha particular selection tool 110 and/or client process 115. Accordingly,in some embodiments, the framework 100 includes metadata that defineshow the population selection engine 105 interacts with one or moreselection tools 110, as well as one or more client processes 115. Hence,in an aspect, the framework 100 includes a container for storing one ormore sets of selection tool metadata 130 (each of which pertains to oneof the selection tools 110 defined to the population selection engine105) and a container for storing one or more sets of selection contextmetadata 135 (each of which pertains to one of the client processes 115defined to the population selection engine.)

The term “container” is used herein to mean any sort of storagemechanism that can be used to store metadata and/or specify the formatof the metadata. In an aspect, the container for a type of metadatamight provide an abstract template to which the stored metadata shouldadhere. In other words, the containers implemented by the populationselection framework might serve as object classes from which actual setsof metadata can inherit properties (such as XML tags, etc.). In a set ofembodiments, for example, a particular type of selection tool might berequired to have a set of selection tool metadata with particularcharacteristics, and the container can be used to ensure that themetadata complies with these requirements. The container can also beused to inform a display of the metadata in a user interface (e.g., byproviding data labels, etc.). Hence, in a sense, the framework 100 canbe considered to include the metadata itself, as the container is usedto provide structure and/or storage for the metadata, which is used bythe population selection engine 105 to interface with the selectiontools 110 and/or client processes 115.

Each set of selection tool metadata 130 defines, within the populationselection engine 105, a particular selection tool 110. The metadata 130can include a variety of information, including without limitationinformation, a name for the tool, information about an implementationclass adapter (sometimes referred to herein as an “application classadapter” and described further below) used by the selection tool 110, amaximum number of data sets to return with the selection tool 110 (whichcan be used, inter alia, to accommodate limitations imposed by theselection tool 110 itself and/or the population selection engine 105),whether a preview feature (described further below) is enabled by theselection tool, and if so, a maximum number of data sets to display inthe preview. In some embodiments, the selection tool metadata 130 mightalso specify labels to be provided by the user interface 125 of thepopulation selection engine 105 when the selection tool 110 is used(merely by way of example, to allow the user to select data fields inthe data source for filter criteria). If the selection tool 110 isaccessible via URL, the metadata might also include information abouthow to access the selection tool 110 by URL (either to invoke the toolor to edit internal parameters of the selection tool 110, e.g., bystoring a URL to the appropriate resource for editing such parameters).

The selection tool metadata 130 might also comprise information that isspecific to the type of selection tool 110 being defined by the metadata130. For example, if the selection tool 110 is a SQL query-based tool,the selection tool metadata 130 might include information about one ormore SQL views to use for the query, and/or the like. This can force theselection tool to provide all necessary fields in the selectionpopulation returned as a result of the SQL query. As another example, ifthe selection tool 110 is a file-based tool and/or an externalapplication, the metadata 130 might include information about thelocation of the tool 110, how to invoke the tool 110, what file supportis provided (e.g., either a location of a hard-coded data source file, aparameter indicating that the user should be provided with a facility tochoose the data source file, and/or the like.

Each set of selection context metadata 135 provides information about aparticular client process 115 defined by that set of metadata 135. Forexample, if the client process 115 is a batch process, the selectioncontext metadata 135 might identify the batch process (e.g., provideinformation about how to access and/or invoke the batch process). If theclient process 115 is an interactive process, the business application175 might a set of display components (which could be user interfacewidgets, windows, web pages, web pages components, etc.) that can beused to interact with the process, and the selection context metadata135 might specify identify the display components (such as, for webcomponents, by URL). (In this way, the user interface 135 of thepopulation selection engine 105 can be used to visually integrate forthe user the population selection engine-specific portions of the userinterface 125 with the interface to the client process 115. Theselection context metadata 135, in an aspect, might specify whichselection tools 110 are allowed to select data for the client process115 (for example, if there is a known limitation in the client process115 that would prevent the use of a particular selection tool 110).Similarly, access control can be implemented on a per-tool 110 basis fora particular client process 115, e.g., by reference to an access controlscheme of the business application 175, and such access controlparameters can be specified by the selection context metadata 135.

In a set of embodiments, the selection context metadata 135 for aparticular client process 115 also includes information specifying howthe client process 115 needs to receive data. Merely by way of example,if the client process 115 requires certain data fields in each data setfor processing, the selection context metadata 135 might specify theserequired fields (e.g., either by specifying the data fields by name orby referencing a database record that specifies the required datafields). There might also be optional data fields (such as a person'sname, which may not be needed by the client process 115 but could beuseful, for example, in displaying a preview of the selected data), andthe selection context metadata 135 might specify these optional datafields as well. In addition, the selection context metadata 135 oftenwill specify a results record, which is a format (e.g., a databaserecord having particular database fields) for the data sets to beprocessed by the client process 115. This results record can bespecified, inter alia, by referencing a target record in a database. Insome cases, the data fields will need to be mapped to the results record(and/or otherwise formatted or converted), and the selection contextmetadata 135 might also comprise information about how the data fieldsshould be mapped, formatted, converted, etc. Merely by way of example,the selection context metadata 135 might define a data conversion fillto apply when mapping a particular data field in a selected data set toa field in the results record (a trivial example, is a conversion of atemperature value from degrees Celsius to degrees Fahrenheit, althoughmuch more complex conversion filters are possible as well.

In some embodiments, the framework 100 includes an applicationprogramming interface (“API”) 150 that provides for consistentcommunication between the population selection engine 105 and a varietyof selection tools 110. In an aspect, the API might comprise anapplication class adapter that includes a set of exposed methods thatthe selection tool must implement to interface with the populationselection engine. In an exemplary embodiment, the following methods(among others) may be implemented: a LaunchTool( ) method, which can beused by the population selection engine 105 to launch (invoke) theselection tool 110; a LaunchToolValid( ) method, which returns a valueindicating whether the current user (or process) has sufficient accessrights and can be used by the population selection engine 105 to ensurethat the user (or process) has sufficient access rights to use theselection tool 110 and/or access the data source 140; an OpenQuery( )method, which can be used by the population selection engine 105 toinstruct the selection tool to open and/or validate the selection and/orselection criteria; an ExecuteToRecord( ) method, which can be used bythe population selection engine 105 to cause the selection tool 110 toselect the desired data sets and return them in an appropriate formatfor processing (including, for example, as a record in a table in thedatabase 120 or another database, for example); an ExecuteToRowSet( )method, which can be used by the population selection engine 105 tocause the selection tool 110 to select the desired data sets and returnthem as a set of rows for processing (merely by way of example, as atemporary set of rows in volatile memory, which might be stored later ina database table); and an ExecuteToHTML( ) method, which can be used bythe population selection engine 105 to cause the selection tool 110 toselect the desired data sets and return them in an appropriate formatfor preview by the user (for example, as an HTML string which can bedisplayed by the user interface 140 in a web browser). In some cases,the filter criteria or search query used to select the data populationcan be passed from the population selection engine 105 to the selectiontool as a parameter, for instance in the ExecuteToRecord( ),ExecuteToRowSet( ) and/or ExecuteToHTML( ) methods. (It should be notedthat the described methods are provided for descriptive purposes andshould not be considered limiting. Various embodiments might implementother types of exposed methods and in fact might use a different type ofAPI altogether.)

The population selection framework 100 (and/or a portion thereof) may beimplemented within the business application 175 and/or may be providedby a standalone application configured to interface with the businessapplication 175. Merely by way of example, in FIG. 1A, the businessapplication 175 includes the population selection engine 105, andmetadata 125, 130, while in FIG. 1B, these components are not includedwithin the business application 175 but instead are configured tointerface with the business application 175. (In the embodimentsillustrated by FIGS. 1A and 1B, the selection tool 110 and data source135 are depicted as residing outside the business application 175, butin some embodiments, one or both of these components may be incorporatedwithin the business application 175 as well.)

Some embodiments of the invention are implemented in a client-servermodel. Merely by way of example, the business application 115 might beinstalled on an application server, and the database 120 might beinstalled on a database server (and/or on the application serveritself). The population selection engine 105 might also be configured torun on the application server. The user interface 125, on the otherhand, might be configured to be displayed on a client computer operatedby a user. The user interface 125 might be provided by a dedicatedclient application in communication with the business application and/orpopulation selection engine, and/or, as described elsewhere herein,might be provided as a set of one or more web pages displayed in a webbrowser on the client computer. The selection tool 110, depending on itsnature, might be installed on either the client computer and/or theserver computer. In any event, a network might be provided (as describedin more detail below) to provide communications between variouscomputers that implement the framework 100.

II. Configuring a Population Selection Engine

As noted above, in many cases, a population selection engine needs to beconfigured to operate with a particular selection tool and/or clientprocess. FIG. 2 illustrates a method 200 of configuring a populationselection engine. The method 200 comprises providing a populationselection framework (block 205), such as the framework 100 describedabove with respect to FIGS. 1A and 1B, to name one example. In anaspect, providing a population selection framework can comprise one ormore of a variety of operations, including without limitation,installing on a computer system a business application (or otherapplication) that includes a population selection framework, providing auser with access to such a framework (e.g., through a businessapplication and/or other application that implements a populationselection framework), executing an application that implements such aframework, and/or the like.

The method 200 further comprises providing a user interface from acomputer system (block 210). As noted above, the user interface might beprovided by the population selection engine itself, from a businessapplication associated with the population selection engine, etc. Alsoas noted above, some operations might be performed on a server computer,while the user interface might be displayed on a client computer (e.g.,as one or more web pages in a web browser on the client computer). Theuser interface can allow the user to interact with the populationselection engine, either to configure the population selection engine,or to use the population selection engine to select data for a clientprocess, as described in further detail below.

At block 215, a set of selection tool metadata is received from the user(e.g., via the user interface). As noted above, in an aspect, the set ofselection tool metadata pertains to a selection tool that can be used bythe population selection engine for selecting data to provide to abusiness application. FIG. 3A is an exemplary screen display thatillustrates one embodiment of a user interface 300 for receiving a setof selection tool metadata for a SQL-query based selection tool. Theuser interface 300 includes data fields for the name of the selectiontool 305, a description of the selection tool 310, a description of theapplication class adapter used by the selection tool 315, whether theselection tool should be usable (active) by the population selectionengine, one or more SQL views to use for the selection tool 320, a label325 to display in the user interface of the population selection engine,a maximum number of data sets to return 330, and a maximum number ofdata sets to preview. The user interface 300 also includes a number offields that specify parameters 340 to use when launching the selectiontool. Using this interface 300, a user can provide selection toolmetadata to the population selection engine, which receives it from theuser interface.

Returning to FIG. 2, at block 220, a set of selection context metadatais received from the user, via the user interface. As noted above, in anaspect, the set of selection context metadata comprises informationabout a first client process that is implemented by the businessapplication (i.e., a business application process) to process dataselected by the selection tool. FIG. 3B is an exemplary screen displaythat illustrates one embodiments of a user interface 350 for receiving aset of selection context metadata. Using the interface 350, the user canprovide metadata about the name of the client process 355 within thebusiness application, as well as display information for the populationselection engine's user interface (such as a context name anddescription), an identification of a process type 360 (which might be abatch process, interactive process, etc.), a status of the clientprocess, such as available to the population selection engine (active)or unavailable (inactive), as well as information 365 about selectiontools that can be used to select data for that client process (and anyaccess restrictions imposed on the use of those tools).

FIG. 3C is another screen display illustrating a user interface 375 thatcan be used to provide metadata defining how the population selectionengine should provide data to the client process. The interface 375provides a data field where the user can specify the results record thatthe process uses 380 and the fields required by the process 385 (which,in this case, are specified by a required fields record, as describedabove. The interface 375 also provides data fields 390 for allowing theuser to define how the required fields should be mapped to the resultsrecord.

Returning once again to FIG. 2, the method 200 further comprisesconfiguring the population selection engine based on the selection toolmetadata and the selection context metadata (block 225). Configuring thepopulation selection engine comprises, in an aspect, storing thereceived metadata and/or reading the metadata upon execution of thepopulation selection engine, so that the population selection engine canproperly interact with the defined selection tools and client processes.

Once the population selection engine has been configured to define aparticular selection tool and/or client process, the user can use thepopulation selection engine to interface with the defined tool and/orprovide data to the defined process. Hence, the method 200 comprises, insome cases, providing (e.g., via the user interface), a display (block230). The display can be used to allow the user to select a definedselection tool (for selecting a set of data) and/or a defined clientprocess (for processing the selected data). Techniques for selectingand/or processing data are described in further detail below.

III. Selecting Data with a Population Selection Engine

As noted above, certain embodiments of the invention can be used toselect data to be processed by a business application (and, optionally,to process the data with a client process in the business application).FIG. 4 illustrates a method 400 of selecting and/or processing data, inaccordance with one set of embodiments. (The method 400 is describedherein generally with respect to the framework 100 of FIGS. 1A and 1B;it should be appreciated, however, that the method 400 is not limited toany particular structural implementation or software architecture;similarly, the framework 100 of FIGS. 1A and 1B can operate inaccordance with the method 400, as well as other modes of operation.)

The method 400 comprises providing, at a computer system, a populationselection engine (block 400). As noted above, in an aspect, a populationselection engine can be used to select data (via a selection tool, forexample) and/or format/convert data to be processed by a businessapplication. Providing a population selection engine can comprise, interalia, installing on a computer system a software application thatcomprises a population selection engine, configuring a populationselection engine (as described above with respect to FIG. 2, forexample), providing a user with access to a population selection engine(including, for example, executing an application that implements apopulation selection engine), and/or the like.

The method 400 further comprises maintaining metadata at the computersystem (block 410). The metadata, includes, in an aspect, a set ofmetadata for each of one or more selection tools that are available tothe population selection engine and/or a set of metadata for each of oneor more client processes to which the population engine can providedata. Some examples of such metadata are described above. In aparticular aspect, as noted above, a population selection framework maycomprise containers for storing metadata, and maintaining metadata cancomprise creating the metadata, storing the metadata in thecontainer(s), updating the metadata, accessing the metadata, and/or thelike.

The method 400 also comprises providing, from the computer system a userinterface (such as the user interface 125 described above with respectto FIGS. 1A and 1B) for the user to interact with the populationselection engine (block 415). An example of such a user interface 500 isillustrated with respect to FIG. 5. The user interface 500 can be usedto allow a user to operate the population selection engine to selectdata and provide the data to a client process. The exemplary interface500 includes a data field for the user to choose a desired selectiontool 505 to be used select data sets to be processed, a data field forthe user to identify a name of a defined query 510 to be performed bythe selection tool, an option to launch a query manager 515, which canbe used to edit the identified query, and an option to preview theselected data sets 520. The exemplary interface 500 also includes a setof display components 525 from the selected client process (which arevisually integrated, as described above, on the same web page as theuser interface for the population selection engine itself), which allowthe user to provide process-specific parameters to be used whenprocessing the selected data.

Returning to FIG. 4, at block 420, the method 400 comprises identifyingthe client process for which data is to be selected and/or specifyingprocess-specific parameters for processing of data with the process (forexample, by reference to FIG. 5, using the display components 525 forthe process, as specified by the selection context metadata). In someembodiments, this might include receiving a selection of a clientprocess from among several defined client processes, which can bedisplayed by an interface similar to the interface 500 of FIG. 5. Inother embodiments, the client process might be identified in other ways.Merely by way of example, in one implementation, the user might invokethe client process from within the business application, and thebusiness application then might invoke the population selection engineto select data for the process, which already has been selected bydefault by the business application.

At block 425, the method comprises receiving, via the user interface,identification of a selection tool to be used to select data to beprocess with the business application (for example, by receiving inputfrom the appropriate data field 505 on the interface 500 of FIG. 5).

Optionally, the method might comprise receiving a set of filter criteriato be used to select data from the data source (block 430). This filtercriteria might be received from the user and/or via the user interface.Merely by way of example, the user interface might provide an inputfacility (such as the data field 510 on FIG. 5 and/or a query manager,which can be used to assist the user in creating a SQL statement to useas a filter criteria) for the user to provide a SQL statement (orstatements) that specify a query to be performed by the selection toolto identify data sets to be selected. As another example, the userinterface might be configured to allow the user to specify analgorithm/formula that should be provided to a search tool to selectdata from a spreadsheet, a search criteria for searching a flat file,etc.

At block 435, the method comprises identifying a data source (such as adata source 125 described above with respect to FIGS. 1A and 1B), whichcomprises the data to be processed with the business application. Insome cases, the data source might be identified based on input receivedfrom the user (e.g., via the user interface). Merely by way of example,if the data source is a spreadsheet, flat file, etc., the user mightidentify the location of the data source (e.g., by typing in a filepath, by browsing a directory structure, etc.). In other cases, the datasource might be identified with a different technique. Merely by way ofexample, in some cases, the selection tool metadata for the chosenselection tool might specify the data source that is to be used withthat selection tool.

Optionally, the method 400 might include determining whether the userhas sufficient access rights to use the chosen selection tool and/or toaccess the chosen data source (block 440). As noted above, in some casesa selection tool API will include a method that allows the populationselection engine to inquire of the selection tool whether the user hassufficient access rights. Hence, determining whether the user hassufficient access rights might comprise relying on an access controlscheme of the selection tool. Merely by way of example, the populationselection engine might be configured to call the appropriate method inthe API, with the user's ID (or other credentials) as a parameter, andthe method might return a Boolean value indicating whether the user isallowed to use the selection tool and/or access the data source. Inother embodiments, the population selection engine might rely on its ownaccess control scheme (e.g., the population selection engine might haveits own authentication and/or authorization modules). In yet otherembodiments, the population selection engine might rely on the accesscontrol scheme of the business application itself (for example, inembodiments in which the population selection engine is incorporatedwithin the business application and/or accessed via the businessapplication.)

At block 445, the selection tool is invoked by the population selectionengine. In some embodiments, the selection tool is invoked based on someor all of the metadata maintained by the population selection engine.Merely by way of example, the metadata, as noted above, might specify alocation of the population selection engine, a method of invoking thepopulation selection engine, etc. In some cases, the selection tool isfirst launched using an API, such as by using a LaunchTool( ) method (ora similar method) and is then invoked via the API (using, for example,an ExecuteToRecord( ) or ExecuteToHTML( ) method (or similar methods).As noted above, in some cases, the invocation of the selection tool isalso based at least in part on user input (such as, for example, theuser's choice of which selection tool to use, the filter criteriaprovided by the user, etc.) In a particular embodiment, the filtercriteria is passed to the selection tool as a parameter to theinvocation method. The technique for invoking the selection tool isdiscretionary, however, so long as the selection tool is successfullyinvoked and any necessary filter criteria are provided to the selectiontool.

At block 450, the selection tool selects one or more sets of data in thedata source, in accordance with the instructions received from thepopulation selection engine (which might include, for example, a filtercriteria to apply). The nature of the sets of data generally will dependon the type of selection tool and/or data source chosen. For example, ifthe data source is a database table, the data sets might comprisesrecords from the table (and/or particular data fields from thoserecords), while if the data source is a flat file, the data sets mightcomprise strings of data (which might be delimited in some fashion).Similarly, the techniques used by the selection tool to select sets ofdata from the data source will also generally depend on the nature ofthe data source and/or selection tool. Given the wide variety of datasources and selection tools that can be supported by the populationselection engine, there is a correspondingly wide variety of dataselection and gathering techniques that might be used. In one aspect,the population selection engine is agnostic to the techniques used bythe selection tool to select and/or gather data sets, since thepopulation selection framework serves to isolate the populationselection engine from these implementation-specific details. Moreprecisely, in a set of embodiments, when the population selection engineinvokes the selection tool, it can expect to receive the data sets fromthe selection tool in a specified format, irrespective of the techniquesused by the selection tool to select and/or gather the data sets.

The selection tool then provides the selected data to the populationselection engine, in the format specified by the invocation of theselection tool, and the population selection engine receives theselected data sets (block 455). For example, if the ExecuteToRecord( )method is used to invoke the selection tool, the method might return thedata sets to the population selection engine as a database record and/orset of database records. As another example, if the ExecuteToHTML( )method is used to invoke the selection tool, the data sets might bereturned as an HTML-formatted string suitable for display by thepopulation selection engine in a web browser. In some cases, receivingthe data sets at the population selection engine might comprisereceiving the actual data. In other cases, receiving the data sets mightcomprise receiving references or pointers to the data sets in a database(such as, for example, when the data source is the same database thatstores information for the business application).

In some cases, the population selection engine may be configured todisplay (e.g., via the user interface) a preview of the selected datasets (block 460). This display can provide the user with a preview ofthe data to be processed before the user has to commit to actuallyprocessing the data. In this way, the user can ensure that the correctdata sets have been selected. If necessary, the user can abort theprocessing at this point, revise the filter criteria, and re-execute theselection process to select more appropriate data for processing.

If necessary, the received data sets can be reformatted and/or otherwiseconverted by the population selection engine into a format required bythe client process at the business application. As noted above, in someembodiments, the selection context data for a particular client processmight specify that data from a data source needs to be mapped toparticular data fields or placed in a particular format for processingby the process. In such cases, the population selection engine, byreference to the metadata, will reformat or convert the selected datasets as necessary before (or while) providing the data to the clientprocess.

At block 470, the selected data sets are provided to the client process.Once again, the way in which the data sets are provided to the processdepends on the nature of the data sets and the nature of the clientprocess. In some cases, if the data sets reside in database tableswithin the business application (or that are accessible by the businessapplication), providing the data sets might simply comprise providingreferences or pointers to the data sets. In other cases (such as whenthe data sets are selected from a data source outside the businessapplication), the data sets might be stored in a result record indatabase table accessible by the business process. In yet other cases,the data sets might be fed as raw (or formatted) data directly from thepopulation selection engine to the client process.

The client process at the business application then processes each ofthe selected data sets (block 475). In some cases, the client process iscalled or invoked by the population selection engine. In other cases,the process might already be running. The client process, as notedabove, can be configured to process the selected data sets eitherinteractively and/or in a batch mode. The operations performed by theclient process in processing the data sets vary widely depending on thenature of the client process. Those skilled in the art will recognizethat a typical business application can perform a variety of processes(which might be pre-defined by the application, defined by the user,etc.) on a data set, and any of such processes can be supported byparticular embodiments of the invention. In some cases, the processingwill modify a database used by the business application (block 480),such as by creating new records in a table of the database, modifyingexisting records, etc. Once again, those skilled in the art willappreciate that a business application process can perform a widevariety of operations that will modify a database (and/or tables, rows,etc. therein), and that any of such operations might be implemented bythe client processes for which the population selection engine selectsdata. Merely by way of example, if the data sets are selected from adata source external to the database, modifying the database mightcomprise creating one or more new records in the database, correspondingto each of the selected data sets. On the other hand, if the database isthe data source, then the client process might modify the database byupdating the records that comprise and/or correspond to the selecteddata sets.

In some embodiments, the method 485 is configured to display (e.g., viathe user interface) an indication of a result of the processing. In somecases, this indication might simply be a notice that processing hassuccessfully completed, a warning about any data sets that were notsuccessfully processed, etc. In other cases, the indication mightprovide additional details (including, for example, the number of datasets processed, number of database records updated or created, etc.). Insome cases, displaying the indication of a result of the processingmight comprise writing the indication to a log file, emailing theindication to an email address of the user or another administrator,etc.

IV. Population Update Framework

Another set of embodiments provides flexibility in updating businessobjects (usually, although not necessarily, in the context of a businessapplication) through a robust software framework for updating a datapopulation. In an aspect, such embodiments can use the populationselection tools described above to select business objects to beupdated. In another aspect, the update framework of various embodimentsmay incorporate (or be incorporated within) a population selectionframework as described above, and/or an integrated software applicationmay perform both data population and update functionality. (As usedherein, the term “business object” refers to any collection of data thatcan be processed using the tools described herein. Business objectsinclude, but are not limited to, database tables, database records,instances of object-oriented classes (e.g., Java classes), text files,spreadsheet files, and/or the like.)

In some cases, update utilities provided by certain embodiments may beimplemented in conjunction with a business application and/or may beincorporated within a business application. There are a variety ofpossible configurations. FIGS. 8A-8C illustrate just a fewpossibilities, although one skilled in the art will recognize that otherarrangements are possible within the scope of the invention.

FIG. 8A, for example, illustrates a population update framework,implemented as an update utility (referenced generally as 800). In FIG.8, the update utility 800 is implemented within a business application.805, in accordance with some embodiments. In the illustrated embodiment,the framework 800 comprises a population update engine 810. As usedherein, the term “population update engine” is used to refer to anysoftware tool, application and/or component that can be used to updatedata within a business object (e.g., in the context of a businessapplication), and/or optionally, to modify, format and/or convert thedata for storage. In this way, the population update engine 810 canserve as an intermediary between a selection tool that selects data tobe updated and an update tool 815 that actually updates the data. Insome cases, as in the embodiment illustrated by FIG. 8A, the selectiontool may include a population selection engine 105 and/or populationselection framework, as described in detail above.

Hence, in one aspect, embodiments can be used to provideinteroperability between selection tools and update tools 815 thatpreviously were inoperable, by providing a standardized framework 800for this operability. Merely by way of example, as noted above, toolsprovided by certain embodiments can extend the logic and/orfunctionality of business applications outside the traditional databasetables used by the business application, while in another aspect, thesetools can be used to provide more flexible techniques for modifying datawithin such database tables.

In an aspect, the population update engine 810 can communicate with apopulation selection framework (and, in particular, the populationselection engine 105) to interface with a variety of data sources 140 toselect and/or obtain the data for processing (for example, in the mannerdescribed above). More generally, however, within the context of thepopulation update tools described in this section, the populationselection engine 105 can be any type of software tool, applicationand/or component that is configured to access a data source, select datafrom the data source, and/or provide the data to the population updateengine 810. Several embodiments of the population selection engine 105are described above in Sections I-III.

The population update engine 810 is configured to interface both withthe population selection engine 850 and with the update tool 815. In oneaspect, the population update engine 810 employs a plurality of adapterinterfaces 820, each of which is configured to interact with an API 825(or other inter-process/inter-application communication facility)provided by the update tool. By using an adapter interface 820 that iscustomized for a particular update tool 815, the population updateengine 810 itself can be generalized to operate with a number of updatetools 815.

One benefit of certain embodiments is that a wide variety of updatetools 815 (and, correspondingly, a wide variety of business objects 840)can be supported by the update utility 800. Such update tools caninclude, without limitation, desktop applications (such as spreadsheetprograms, which can treat a spreadsheet file as a business object to beupdated), standard and/or proprietary data access utilities, databasemanagement systems (and/or procedures within those systems), businessapplications, and/or the like. Merely by way of example, the businessapplication processes described above in Sections I-III can beconsidered update tools 815 in accordance with some embodiments.

In some embodiments, the framework 800 might also comprise a userinterface 830 (which might be a graphical user interface provided by thebusiness application 805, an interface provided by a standalone softwareapplication that implements the framework 800 and/or a selection engine105, and/or the like.) Similar to the interface for the populationselection framework described above, the user interface 845 may beprovided as a web interface (that is, a set of one or more web pagesserved by a web server and/or application server and displayed by a webbrowser on a client computer, as described in more detail below).

The framework 800 also provides for update context metadata 835, whichan be stored in a container, similar to the metadata described above inSections I-III. The update context metadata 835 can serve any of severalfunctions in the operation of the update utility 800. A first type ofupdate context metadata 835 defines a relationship between thepopulation update engine 810 and each of the available update tools 815.In particular, this type of metadata 835 identifies an appropriateadapter interface 820 for the update tool 815. This type of metadata 835might also identify the functionality of the update tool 815 (e.g., whattypes of business objects 840 the update tool can update, and the like).

A second type of update context metadata 835 can be used to describe theproperties of business objects 840 themselves. Merely by way of example,in some cases, as noted above, certain data elements in a businessobject 840 may need to be protected, as their modification may adverselyimpact the business object 840 of which they are a part. Hence, thissecond type of update context metadata 835 can be used to define whichdata elements within a business object 840 are permissible to modify. Inaddition, this second type of update context metadata 825 might describethe structure of the business object 840 (including, without limitation,a description of the different data elements and their types,specification of access methods, and/or the like), although in someembodiments, the update tool 815 itself is configured to account forthis type of information.

In some cases, the update context metadata 835 might also compriseinformation about available population selection engines 105 and/ortools, including without limitation, metadata that describes how thepopulation update engine 810 should interface with such engines/tools,what data sources 140 are appropriate for such tools, and/or the like.Merely by way of example, in some cases, a user might select a datasource from which to select the data population, and update engine mightconsult appropriate metadata 835 to determine which vehicle (e.g.,selection engine 105, selection tool, etc.) should be used to select thedata population, based on information in the metadata about that datasource and/or data population. In other cases, however, the user mightspecify which population selection engine 105 and/or selection tool touse. In still other cases, the update engine 810 might use thepopulation selection framework described above as its default (or only)vehicle for selecting data, and the update engine 810 therefore mightrely on the population selection engine 105 to determine appropriateselection tools, etc., perhaps in the fashion described above.

The operation of the population update engine 810 is described infurther detail below; in general, however, the population update engine805 interfaces with the population selection engine 850 to select andretrieve data from a data source 840 based, in some cases, on user inputreceived via user interface 830. The population update engine 805 isconfigured to receive a selection one or more business objects (i.e.,sets of data) (referred to herein as a data “population”) from apopulation selection tool 015, based on data from a data source 840 andto provide that data population to the update tool 815 for dataupdating. (It should be noted that the terms “receive” and “provide” areused broadly in this context to include receiving and/or providingpointers and/or other references to the selected business objects 840,rather than passing the business objects themselves (although this ispossible as well).

The data source 140 can be any of a variety of data sources, includingwithout limitation a database and/or database table (which, in somecases, might be the database used by the business application 805), aspreadsheet, a flat file, a data store for a separate application (suchas an email application, etc.), and/or any of a variety of data sources.In fact, one benefit of certain embodiments is the wide ranges ofdifferent data sources that can be used select a data population to beupdated—as noted above, by using an appropriate population selectionengine 105, virtually any type of data source may be supported.

It should be noted that, in some cases, the data source 140 may be adata store that holds the business objects 840 to be updated, but thisneed not necessarily be the case. Merely by way of example, in someimplementations, the data source 140 might be a database, and thebusiness objects 840 might be records within the database. By contrast,in other cases, the data source 140 might be the database, but thebusiness objects might be a set of instances of a Java class outside thedatabase. As yet another example, the data source 140 might be aspreadsheet of comprising multiple entries, and the business objects 840might be records in a database; the entries in the spreadsheet mightprovide selection criteria defining which records in the database shouldbe selected.

Although only one population selection engine 105 and update tool 815are depicted in FIGS. 8A and 8B, a single population update engine 805can support any number of either of these components, for examplethrough the use of appropriate adapter interfaces 820 and/or updatecontext metadata 835 specific to each update tool 815.

As illustrated by FIG. 8A, the update utility 800 (and/or a portionthereof) may be implemented within a business application 805 and/or maybe provided by a standalone application configured to interface with thebusiness application 805. Merely by way of example, in FIG. 8A, thebusiness application 875 includes the population update engine 805, andmetadata 835, while in FIG. 8B, these components are not included withinthe business application 8805 but instead are configured to interfacewith the business application 805. As another example, FIG. 8Cillustrates a update utility incorporated within a business application805 but configured to use an update tool 815 outside the businessapplication 805 to update a business object 840 also outside thebusiness applications. A variety of other configurations can besupported as well. Merely by way of example, in the embodimentsillustrated by FIGS. 8A-8C, the population selection engine 105 and datasource 140 are depicted as residing outside the business application805, but in some embodiments, one or both of these components may beincorporated within the business application 805 as well.)

The tools provided by some embodiments may be implemented in aclient-server model. Merely by way of example, the business application805 might be installed on an application server, and the businessobjects 840 might be records in a database installed on a databaseserver (and/or on the application server itself). The population updateengine 805 might also be configured to run on the application server.The user interface 830, on the other hand, might be configured to bedisplayed on a client computer operated by a user. The user interface830 might be provided by a dedicated client application in communicationwith the business application 805 and/or population update engine 810,and/or, as described elsewhere herein, might be provided as a set of oneor more web pages displayed in a web browser on the client computer. Inany event, a network might be provided (as described in more detailbelow) to provide communications between various computers thatimplement the framework 800.

V. Configuring a Population Update Engine

Somewhat similarly to the population selection engine described above,an update utility, in many cases, may need to be configured to operatewith a particular population selection engine and/or client process.FIG. 9 illustrates a method 900 of configuring a population updateengine. The method 900 comprises providing a population update framework(block 905), such as one of the frameworks described above with respectto FIGS. 8A-8C, to name one example. In an aspect, providing apopulation update framework can comprise one or more of a variety ofoperations, including without limitation, installing on a computersystem a business application (or other application, such as an updateutility) that includes a population update framework, providing a userwith access to such a framework (e.g., through a business applicationand/or other application that implements a population update framework),executing an application that implements such a framework, and/or thelike.

The method 900 further comprises providing a user interface from acomputer system (block 910). As noted above, the user interface might beprovided by the population update engine itself, from a businessapplication associated with the population update engine, from apopulation selection engine, etc. Also as noted above, some operationsmight be performed on a server computer, while the user interface mightbe displayed on a client computer (e.g., as one or more web pages in aweb browser on the client computer). The user interface can allow theuser to interact with the population update engine, either to configurethe population update engine, or to use the population update engine toupdate data for a client process, as described in further detail below.

At block 915, a set of update context metadata is received from theuser, via the user interface. As noted above, in an aspect, the set ofupdate context metadata may comprise one or more different types ofinformation, including without limitation information about one or morebusiness objects that are implemented (including, but not limited tobusiness objects that are by a business application), information aboutavailable update tools, information about selection tools and/or thelike. Merely by way of example, FIG. 10 is an exemplary screen displaythat illustrates one embodiment of a user interface 1000 for receiving aset of update context metadata about a type of business object (in thiscase, the business object type is a database record, although othertypes of business objects can be supported as well—as noted above, abusiness object can be, in various embodiments, a database record, aJava structure, a spreadsheet, a flat file, etc.) In an embodiment,using the interface 1000, the user can provide context metadata aboutthe fields of a record 1010, previously selected, that should be madeavailable for update (e.g., fields that will not adversely affect theoperation of the database if they are modified by the update process).(While the illustrated example allows selection of fields in thedatabase record, other types of data elements may be selected, dependingon the type of business object about which metadata is being provided.)

FIG. 10 also illustrates that context metadata about the fields in therecord may also be designated as updatable. The user interface allowsfor input of a record field 1015 that can be modified. An interfaceelement, e.g., a drop-down menu 1035, allows for selection of a fieldwithin the record 1010 (in an embodiment, the menu 1035 may be populatedwith all of the fields in that type of record, for example, byinterrogating the database containing the record to obtain theinformation, by hard coding the field names into the utility, etc. Alabel 1020 identifying a description associated with the selected fieldmay also be displayed to facilitate selection by the user. Additionalfields to be exposed to the update process can be selected by usingother user interface devices, e.g., an add button 1030, to indicate thatthe user desires to select additional fields in the database to bedesignated as available to the update utility. Upon activation of thebutton 1030, interface elements 1025, 1040 for selecting an additionalfield are displayed. (Similarly, an interface element, such as a deletebutton 1045, can be provide to allow a user to remove a selected fieldfrom the list of fields available. The input process allows forselection of one or more portions or components in the business objectthat can be updated. The input process also ensures that portions of thebusiness object that are not to be updated are also protected by notbeing selected.

Returning once again to FIG. 9, the method 900 further comprisesconfiguring the population update engine based on the update contextmetadata (block 920). Configuring the population update enginecomprises, in an aspect, storing the received metadata (e.g., in anappropriate container) and/or reading the metadata upon execution of thepopulation update engine, so that the population update engine canproperly interact with the population selection engine and/or variousupdate tools (and/or their APIs).

Once the population update engine has been configured to define aparticular business object and/or client process, the user can use thepopulation update engine to interface with a vehicle for selecting data(e.g., a population selection engine) and/or provide data to definedupdate tools. Hence, the method 900 comprises, in some cases, providing(e.g., via the user interface), a display (block 925). The display canbe used to allow the user to select a defined a population selectionengine (for selecting a data population) and/or an update tool (forupdating data in the business objects in the selected data population).Techniques for updating and/or processing data are described in furtherdetail below.

VI. Updating Data with a Population Update Engine

As noted above, some embodiments provide tools that can be used toupdate a business object to be processed by a business application (and,optionally, to process the data with a client process in the businessapplication) and/or stored in a database. FIG. 11 illustrates a method1100 of updating a business object, in accordance with one set ofembodiments. (The method 1100 is described herein generally with respectto the framework of FIGS. 8A-8C; it should be appreciated, however, thatthe method 1100 is not limited to any particular structuralimplementation or software architecture; similarly, the frameworks ofFIGS. 8A-8C can operate in accordance with the method 1100, as well asother modes of operation.)

The method 1100 comprises providing, at a computer system, a populationupdate engine (block 1105). As noted above, in an aspect, a populationupdate engine can be used to update data in one or more business objectsin a data population. Providing a population update engine can comprise,inter alia, installing on a computer system a software application thatcomprises a population update engine, configuring a population updateengine (as described above with respect to FIG. 9, for example),providing a user with access to a population update engine (including,for example, executing an application that implements a populationupdate engine), and/or the like.

The method 1100 further comprises maintaining metadata at the computersystem (block 1110). The metadata, includes, in an aspect, a set ofcontext metadata for each type of business object that can be updated,metadata for the population selection engine itself, metadata forvarious selection vehicles, and/or metadata for various update tools towhich the population update engine can provide data. Some examples ofsuch metadata are described above. In a particular aspect, as notedabove, a population update framework may comprise containers for storingmetadata, and maintaining metadata can comprise creating the metadata,storing the metadata in the container(s), updating the metadata,accessing the metadata, and/or the like.

The method 1100 also comprises providing, from the computer system, auser interface (such as the user interface 830 described above withrespect to FIGS. 8A and 8B) for the user to interact with the populationupdate engine (block 1115). An example of a screen display of one suchuser interface 1200 is illustrated with respect to FIG. 12. The userinterface 1200 can be used to allow a user to operate the populationupdate engine to update data and provide the updated data to a clientprocess. The exemplary interface 1200 includes an interface element(e.g., a text entry field, pulldown menu, combobox, etc.) 1205 for theuser to choose a data source to be subject to the update, and one ormore interface elements (collectively, 1210) to provide selectioncriteria to be provided to the selection tool to define a portion of thebusiness object. The interface 1200 may also include an interfaceelement (such as a pulldown menu 1215) for the user to identify aselection tool as to select the data population to be updated, and,optionally, one or more other interface elements for providingadditional data specific to the selected selection tool (such as, in thecase of a selection tool that selects from a database, a text entryfield 1225 for the user to identify a name of a query to define a viewin the database to be used to perform the selection and/or a link 1230to open a query manager. (Because the interface 1200 illustrates anembodiment that implements a selection engine for selecting the datapopulation, many of the interface elements 1205-1230 may operate insimilar fashion to their counterpart elements 505-515 in the interface500 described above with respect to FIG. 5. If other selection vehiclesare used, these interface elements can vary according to theimplementation of those selection vehicles).

The interface 1200 may also provide an interface element 1235 thatallows the user to preview the selected data population prior toexecution of the update, e.g., in the manner described above. Theexemplary interface 1200 also includes a field selector interfaceelement 1240 to select a data element be updated. In an aspect, thefield selector interface element 1240 will display (and therefore allowselection of) only data elements that have been defined (e.g., bymetadata) as being available for update, as described above. A valueselector interface element 1245 allows the user to input an update valuefor the selected field (i.e., a value to be inserted into the dataelement during the update process). This input value can be a constantvalue, and/or it can be a formula, which may be evaluated at updateruntime to determine a constant update value and/or which may itself beinserted as the update value. In embodiments, the value selectorprovides a defined set of values from which the user can select, allowsfor entry of one or more values. This behavior may be defined (e.g., bythe metadata) according to the type of data element. Merely by way ofexample, if a data element is of a Boolean type, the interface element1245 might allow selection of only Boolean values, while if the dataelement is of integer type, the interface element 1245 might allow inputof any integer value. (Data type validation may be performed on theprovided on the input, if text input is allowed.)

An interface element 1250 may be provided to allow the user to selectadditional data elements for updating. Upon selection of this interfaceelement 1250, the interface 1200 provides an additional set of interfaceelements similar to those elements 1240, 1245 described above.

Returning to FIG. 11, at block 1120, the method 1100 comprises receivinguser input (e.g., via a user interface, such as the user interfacedescribed above). Depending on the embodiment, this user input canidentify the data population from which business objects are to beselected, a selection tool for selecting the business objects, an updatetool to use for the update, and/or the like. Based on the user input,the method identifies a data population to be updated (block 1125). Insome embodiments, identifying the data population comprises invoking aselection tool (e.g., using a population selection engine) to select thepopulation based on selection criteria provided by the user, perhaps inthe manner described above in Section III and/or via the user interface1200 illustrated by FIG. 12. In some cases, identifying the datapopulation comprises identifying a data source from which the datapopulation should be drawn (block 1130), e.g., based on input from theuser, based on update context metadata about the business objects in thedata population, etc.

In other embodiments, the data population might be identified in otherways. Merely by way of example, in one implementation, the user mightaccess a business object from within a business application, and thebusiness application then might invoke the population update engine toupdate data for the business object, which already has been selected bydefault by the business application.

The method 1100 also includes identifying an update tool to update thebusiness objects in the selected data population (block 1135). In someembodiments, the update tool may be identified implicitly, for example,based on update context metadata for the selected data population (whichmight specify an appropriate update tool). In other cases, only oneupdate tool may be configured and/or there may be a default update tool.In other embodiments, the update tool may be identified explicitly(e.g., by the user providing input on which update tool should be used).

Optionally, the method 1100 might include determining whether the userhas sufficient access rights to use the chosen update tool and/or toaccess the chosen data source (block 1140). In some cases, the API foran update tool API may include a method that allows the update engine toinquire of the update tool whether the user has sufficient accessrights. In other cases, the population update engine might receive,e.g., from the user, a set of user credentials and attempt to access theupdate tool (and, by the extension, the update tool might attempt toaccess the business objects to be updated), using these credentials,such that the business objects (and/or an application that manages thebusiness objects, such as a DBMS, a business application, etc.) providesaccess control for the update process itself. Hence, determining whetherthe user has sufficient access rights might comprise relying on anaccess control scheme external to the update utility itself. Merely byway of example, the population update engine might be configured to callthe appropriate method in the API for the update tool, with the user'sID (or other credentials) as a parameter, and the method might return aBoolean value indicating whether the user is allowed to use the updatetool and/or access the data source. In other embodiments, the populationupdate engine might rely on its own access control scheme (e.g., thepopulation update engine might have its own authentication and/orauthorization modules). In still other embodiments, the populationupdate engine may provide its own access control scheme (perhapscontrolled by update context metadata) and/or rely on access controlsprovided by a population selection engine. There are a wide variety ofways in which access control can be implemented in accordance withvarious embodiments.

At block 1145, the population selection engine determines one or moredata elements that can be modified in each of the business objects inthe data population. (In one aspect, each of the business objects in adata population is of a common type, i.e., has the same data elements asthe other business objects in the data population, although of course,these data elements may have different values in each respective dataobject.) As noted above, update context metadata can specify, for aparticular type of business object, the data elements that are availableto be updated (e.g., those elements whose modification will notadversely affect the operability of the business object), so thisdetermination can be based on such metadata. Essentially, the populationupdate engine is configured only to update data elements designated bythe metadata as being updatable.

In some embodiments, the population update engine displays for the user(e.g., via the user interface) one or more data elements that can bemodified (block 1150). One example of such a display is the userinterface 1200 described above. The user then selects the desired dataelements to be updated and/or provides input on the update values foreach of the data elements, as described above with respect to FIG. 12,for example. Upon receiving this input at block 1155 (again, e.g., viathe user interface), the population selection engine evaluates anyformulas provided by the user as the basis for the update value toderive respective values for the data element in each of the businessobjects to be updated (block 1160) (or, optionally does not evaluate theformula(s) but instead passes them to the update tool, which mightitself evaluate the formula(s) or might merely insert the formula(s)themselves as the updated value of the data elements in the businessobjects), depending on configuration options, which may be specified byupdate context metadata.

In some cases, the population update engine may be configured to display(e.g., via the user interface) a preview of the updated business objects(block 1165). This display can provide the user with a preview of theupdated data before the user has to commit to actually updating andstoring the data. In this way, the user can ensure that the correct datasets have been updated and the updates have been made correctly to thedata sets. If necessary, the user can abort the update process at thispoint, revise the update values and/or selection of data elements,and/or the like.

At block 1170, the population update engine invokes the update toolidentified as the proper update tool to use in this instance (block1170). noted above, in some cases, invoking an update tool comprisesaccessing an API of the update tool (block 1175), using, for example, anadapter interface as described above. In an embodiment, invoking theupdate tool comprises providing the data population (again, either byactually passing the data objects in the data population or passing areference to the business objects) to the update tool, along withinformation specifying the data element(s) to be updated in eachbusiness object and the value(s) with which those element(s) should beupdated.

At block 1180, the update tool updates the specified data element(s) ineach business object in the data population with the specified updatevalues. Necessarily, the procedures used by the update tool will dependon the nature of the business objects being updated and/or thefunctionality of the update tool itself. As noted above, the updateutility (and, specifically, the population update engine) can beconsidered, in many cases, agnostic of the techniques used by the updatetool—indeed, one benefit of many embodiments is the fact that the updateutility does not need to be aware of how the update tool itselfoperates. To list a few examples, however, the update tool might callone or more SQL procedures to update records in a database, might call abusiness application process to add, modify and/or delete businesstransactions in the business application, and/or the like.

In some embodiments, the method is configured to provide an updatestatus that provides an indication of the result of the update process(block 1185), e.g., by displaying a status indication via the userinterface. In some cases, this indication might simply be a notice thatthe update has successfully completed, a warning about any businessobjects that were not successfully updated, etc. In other cases, theindication might provide additional details (including, for example, thenumber of business objects updated, etc.). In some cases, providing theindication of a result of the updating might comprise writing theindication to a log file, emailing the indication to an email address ofthe user or another administrator, etc.

VII. Exemplary Hardware and Software Implementations

FIG. 6 provides a schematic illustration of one embodiment of a computersystem 600 that can perform the methods provided by various embodiments,as described herein, and/or can function as a computer system (includingwithout limitation a server computer, a client computer, etc.). Itshould be noted that FIG. 6 is meant only to provide a generalizedillustration of various components, any or all of which may be utilizedas appropriate. FIG. 6, therefore, broadly illustrates how individualsystem elements may be implemented in a relatively separated orrelatively more integrated manner.

The computer system 600 is shown comprising hardware elements that canbe electrically coupled via a bus 605 (or may otherwise be incommunication, as appropriate). The hardware elements can include one ormore processors 610, including without limitation one or moregeneral-purpose processors and/or one or more special-purpose processors(such as digital signal processing chips, graphics acceleration chips,and/or the like); one or more input devices 615, which can includewithout limitation a mouse, a keyboard and/or the like; and one or moreoutput devices 620, which can include without limitation a displaydevice, a printer and/or the like.

The computer system 600 may further include (and/or be in communicationwith) one or more storage devices 625, which can comprise, withoutlimitation, local and/or network accessible storage and/or can include,without limitation, a disk drive, a drive array, an optical storagedevice, solid-state storage device such as a random access memory(“RAM”) and/or a read-only memory (“ROM”), which can be programmable,flash-updateable and/or the like. The computer system 600 might alsoinclude a communications subsystem 630, which can include withoutlimitation a modem, a network card (wireless or wired), an infra-redcommunication device, a wireless communication device and/or chipset(such as a Bluetooth™ device, an 802.11 device, a WiFi device, a WiMaxdevice, cellular communication facilities, etc.), and/or the like. Thecommunications subsystem 630 may permit data to be exchanged with anetwork (such as the network described below, to name one example),and/or any other devices described herein. In many embodiments, thecomputer system 600 will further comprise a working memory 635, whichcan include a RAM or ROM device, as described above.

The computer system 600 also can comprise software elements, shown asbeing currently located within the working memory 635, including anoperating system 640 and/or other code, such as one or more applicationprograms 645, which may comprise computer programs provided by variousembodiments, and/or may be designed to implement methods, and/orconfigure systems, provided by various embodiments, as described herein.Merely by way of example, one or more procedures described with respectto the method(s) discussed above might be implemented as code and/orinstructions executable by a computer (and/or a processor within acomputer). A set of these instructions and/or code might be stored on acomputer readable storage medium, such as the storage device(s) 625described above. In some cases, the storage medium might be incorporatedwithin a computer system, such as the system 600. In other embodiments,the storage medium might be separate from a computer system (i.e., aremovable medium, such as a compact disc, etc.), and or provided in aninstallation package, such that the storage medium can be used toprogram a general purpose computer with the instructions/code storedthereon. These instructions might take the form of executable code,which is executable by the computer system 600 and/or might take theform of source and/or installable code, which, upon compilation and/orinstallation on the computer system 600 (e.g., using any of a variety ofgenerally available compilers, installation programs,compression/decompression utilities, etc.) then takes the form ofexecutable code.

It will be apparent to those skilled in the art that substantialvariations may be made in accordance with specific requirements. Forexample, customized hardware might also be used, and/or particularelements might be implemented in hardware, software (including portablesoftware, such as applets, etc.), or both. Further, connection to othercomputing devices such as network input/output devices may be employed.

In one aspect, certain embodiments employ a computer system (such as thecomputer system 600) to perform methods provided by other embodiments.According to a set of embodiments, some or all of the procedures of suchmethods are performed by the computer system 600 in response toprocessor 610 executing one or more sequences of one or moreinstructions (which might be incorporated into the operating system 640and/or other code, such as an application program 645) contained in theworking memory 635. Such instructions may be read into the workingmemory 635 from another machine-readable medium, such as one or more ofthe storage device(s) 625. Merely by way of example, execution of thesequences of instructions contained in the working memory 635 mightcause the processor(s) 610 to perform one or more procedures of themethods described herein.

The terms “machine readable medium” and “computer readable medium,” asused herein, refer to any medium that participates in providing datathat causes a machine to operation in a specific fashion. In anembodiment implemented using the computer system 600, variousmachine-readable media might be involved in providing instructions/codeto processor(s) 610 for execution and/or might be used to store and/orcarry such instructions/code (e.g., as signals). In manyimplementations, a computer readable medium is a physical and/ortangible storage medium. Such a medium may take many forms, includingbut not limited to, non-volatile media, volatile media, and transmissionmedia. Non-volatile media includes, for example, optical or magneticdisks, such as the storage device(s) 625. Volatile media includes,without limitation dynamic memory, such as the working memory 635.Transmission media includes coaxial cables, copper wire and fiberoptics, including the wires that comprise the bus 605, as well as thevarious components of the communication subsystem 630 (and/or the mediaby which the communications subsystem 630 provides communication withother devices). Hence, transmission media can also take the form ofwaves (including without limitation radio, acoustic and/or light waves,such as those generated during radio-wave and infra-red datacommunications).

Common forms of physical and/or tangible computer readable mediainclude, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, or any other magnetic medium, a CD-ROM, any other opticalmedium, punchcards, papertape, any other physical medium with patternsof holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chipor cartridge, a carrier wave as described hereinafter, or any othermedium from which a computer can read instructions and/or code.

Various forms of machine-readable media may be involved in carrying oneor more sequences of one or more instructions to the processor(s) 610for execution. Merely by way of example, the instructions may initiallybe carried on a magnetic disk and/or optical disc of a remote computer.A remote computer might load the instructions into its dynamic memoryand send the instructions as signals over a transmission medium to bereceived and/or executed by the computer system 600. These signals,which might be in the form of electromagnetic signals, acoustic signals,optical signals and/or the like, are all examples of carrier waves onwhich instructions can be encoded, in accordance with variousembodiments.

The communications subsystem 630 (and/or components thereof) generallywill receive the signals, and the bus 605 then might carry the signals(and/or the data, instructions, etc. carried by the signals) to theworking memory 635, from which the processor(s) 605 retrieves andexecutes the instructions. The instructions received by the workingmemory 635 may optionally be stored on a storage device 625 eitherbefore or after execution by the processor(s) 610.

A set of embodiments comprises systems for processing data with abusiness application, for selecting data to be processed, and/or forconfiguring a population selection engine. Merely by way of example,FIG. 7 illustrates a schematic diagram of a system 700 that can be usedin accordance with one set of embodiments. The system 700 can includeone or more user computers 705. The user computers 705 can be generalpurpose personal computers (including, merely by way of example,personal computers and/or laptop computers running any appropriateflavor of Microsoft Corp.'s Windows™ and/or Apple Corp.'s Macintosh™operating systems) and/or workstation computers running any of a varietyof commercially-available UNIX™ or UNIX-like operating systems. Theseuser computers 705 can also have any of a variety of applications,including one or more applications configured to perform methods ofvarious embodiments, as well as one or more office applications,database client and/or server applications, and web browserapplications. Alternatively, the user computers 705 can be any otherelectronic device, such as a thin-client computer, Internet-enabledmobile telephone, and/or personal digital assistant, capable ofcommunicating via a network (e.g., the network 710 described below)and/or displaying and navigating web pages or other types of electronicdocuments. Although the exemplary system 700 is shown with three usercomputers 705, any number of user computers can be supported.

Certain embodiments may operate in a networked environment, which caninclude a network 710. The network 710 can be any type of networkfamiliar to those skilled in the art that can support datacommunications using any of a variety of commercially-availableprotocols, including without limitation TCP/IP, SNA, IPX, AppleTalk, andthe like. Merely by way of example, the network 710 can be a local areanetwork (“LAN”), including without limitation an Ethernet network, aToken-Ring network and/or the like; a wide-area network; a virtualnetwork, including without limitation a virtual private network (“VPN”);the Internet; an intranet; an extranet; a public switched telephonenetwork (“PSTN”); an infra-red network; a wireless network, includingwithout limitation a network operating under any of the IEEE 802.11suite of protocols, the Bluetooth™ protocol known in the art, and/or anyother wireless protocol; and/or any combination of these and/or othernetworks.

Some embodiments can include one or more server computers 715. Each ofthe server computers 715 may be configured with an operating system,including without limitation any of those discussed above, as well asany commercially (or freely) available server operating systems. Each ofthe servers 715 may also be running one or more applications, which canbe configured to provide services to one or more clients 705 and/orother servers 715.

Merely by way of example, one of the servers 715 may be a web server,which can be used, merely by way of example, to process requests for webpages or other electronic documents from user computers 705. The webserver can also run a variety of server applications, including HTTPservers, FTP servers, CGI servers, database servers, Java servers, andthe like. In some embodiments, the web server may be configured to serveweb pages that can be operated within a web browser on one or more ofthe user computers 705 to perform methods of various embodiments.

The server computers 715, in some embodiments, might include one orapplication servers, which can include one or more applicationsaccessible by a client running on one or more of the client computers705 and/or other servers 715. Merely by way of example, the server(s)715 can be one or more general purpose computers capable of executingprograms or scripts in response to the user computers 705 and/or otherservers 715, including without limitation web applications (which might,in some cases, be configured to perform methods of certain embodiments).Merely by way of example, a web application can be implemented as one ormore scripts or programs written in any suitable programming language,such as Java™, C, C#™ or C++, and/or any scripting language, such asPerl, Python, or TCL, as well as combinations of anyprogramming/scripting languages. The application server(s) can alsoinclude database servers, including without limitation thosecommercially available from Oracle, Microsoft, Sybase™, IBM™ and thelike, which can process requests from clients (including, depending onthe configuration, database clients, API clients, web browsers, etc.)running on a user computer 705 and/or another server 715. In someembodiments, an application server can create web pages dynamically fordisplaying the information in accordance with various embodiments, suchas user interfaces for operating and/or configuring a populationselection engine, as described above, for example. Data provided by anapplication server may be formatted as web pages (comprising HTML,Javascript, etc., for example) and/or may be forwarded to a usercomputer 705 via a web server (as described above, for example).Similarly, a web server might receive web page requests and/or inputdata from a user computer 705 and/or forward the web page requestsand/or input data to an application server. In some cases a web servermay be integrated with an application server.

In accordance with further embodiments, one or more servers 715 canfunction as a file server and/or can include one or more of the files(e.g., application code, data files, etc.) necessary to implementmethods incorporated by an application running on a user computer 705and/or another server 715. Alternatively, as those skilled in the artwill appreciate, a file server can include all necessary files, allowingsuch an application to be invoked remotely by a user computer 705 and/orserver 715. It should be noted that the functions described with respectto various servers herein (e.g., application server, database server,web server, file server, etc.) can be performed by a single serverand/or a plurality of specialized servers, depending onimplementation-specific needs and parameters.

In certain embodiments, the system can include one or more databases720. The location of the database(s) 720 is discretionary: merely by wayof example, a database 720 a might reside on a storage medium local to(and/or resident in) a server 715 a (and/or a user computer 705).Alternatively, a database 720 b can be remote from any or all of thecomputers 705, 715, so long as it can be in communication (e.g., via thenetwork 710) with one or more of these. In a particular set ofembodiments, a database 720 can reside in a storage-area network (“SAN”)familiar to those skilled in the art. (Likewise, any necessary files forperforming the functions attributed to the computers 705, 715 can bestored locally on the respective computer and/or remotely, asappropriate.) In one set of embodiments, the database 735 can be arelational database, such as an Oracle database, that is adapted tostore, update, and retrieve data in response to SQL-formatted commands.The database might be controlled and/or maintained by a database server,as described above, for example.

While certain features have been described with respect to exemplaryembodiments, one skilled in the art will recognize that numerousmodifications are possible. For example, the methods and processesdescribed herein may be implemented using hardware components, softwarecomponents, and/or any combination thereof. Further, while variousmethods and processes described herein may be described with respect toparticular structural and/or functional components for ease ofdescription, methods provided by various embodiments are not limited toany particular structural and/or functional architecture but instead canbe implemented on any suitable hardware, firmware and/or softwareconfiguration. Similarly, while various functionality is ascribed tocertain system components, unless the context dictates otherwise, thisfunctionality can be distributed among various other system componentsin accordance with different embodiments.

Moreover, while the procedures comprised in the methods and processesdescribed herein are described in a particular order for ease ofdescription, unless the context dictates otherwise, various proceduresmay be reordered, added, and/or omitted in accordance with variousembodiments. Further, the procedures described with respect to onemethod or process may be incorporated within other described methods orprocesses; likewise, system components described according to aparticular structural architecture and/or with respect to one system maybe organized in alternative structural architectures and/or incorporatedwithin other described systems. Hence, while various embodiments aredescribed with—or without—certain features for ease of description andto illustrate exemplary features, the various components and/or featuresdescribed herein with respect to a particular embodiment can besubstituted, added and/or subtracted from among other describedembodiments, unless the context dictates otherwise. Consequently,although certain features have been described with respect to exemplaryembodiments, it will be appreciated that the invention is intended tocover all modifications and equivalents within the scope of thefollowing claims.

1. A computer readable medium having encoded thereon a set ofinstructions executable by a computer to implement a framework forselecting set of data population to be processed by a businessapplication, the framework comprising: a population selection engineconfigured to provide a set of data, selected from a data source, to abusiness application for processing; one or more sets of selection toolmetadata, including a first set of selection tool metadata comprisinginformation about first a selection tool that can be used by thepopulation selection engine for selecting data to provide to thebusiness application; one or more sets of selection context metadata,including a first set of selection context metadata comprisinginformation about first a business application process implemented bythe business application to process the set of data; and an applicationprogramming interface (“API”) for providing communication between thepopulation selection engine and the one or more selection tools.
 2. Thecomputer readable medium of claim 1, wherein the framework furthercomprises a user interface for allowing a user to select a desiredselection tool having an associated set of selection tool metadata, anda desired business application process having an associated set ofselection context metadata.
 3. The computer readable medium of claim 1,wherein the first set of selection tool metadata comprises anidentification of an application class adapter for the first selectiontool, wherein the application class adapter implements the API.
 4. Thecomputer readable medium of claim 1, wherein the first set of selectiontool metadata comprises an identification of a structured query language(“SQL”) view for the first selection tool to use.
 5. The computerreadable medium of claim 1, wherein the first set of selection toolmetadata comprises one or more labels to be provided by a user interfaceto allow a user to select one or more data fields in the data sourcewhen using the first selection tool.
 6. The computer readable medium ofclaim 1, wherein the first set of selection tool metadata specifies amaximum number of data sets that should be returned by the firstselection tool.
 7. The computer readable medium of claim 1, wherein thefirst set of selection tool metadata specifies a location of the firstselection tool.
 8. The computer readable medium of claim 7, wherein thelocation of the first selection tool is specified as a uniform resourcelocator (“URL”).
 9. The computer readable medium of claim 1, wherein thefirst business application process comprises a batch process, andwherein the first set of selection context metadata identifies the batchprocess.
 10. The computer readable medium of claim 1, wherein the firstset of selection context metadata identifies a set of display componentsthat should be used to display information about the first businessapplication process in a user interface of the population selectionengine.
 11. The computer readable medium of claim 10, wherein the set ofdisplay components comprise a set of web page components.
 12. Thecomputer readable medium of claim 1, wherein the first set of selectioncontext metadata specifies a set of one or more selection tools that canbe used to select data for the first business application process. 13.The computer readable medium of claim 1, wherein the first set ofselection context metadata specifies one or more data fields that arerequired for the first business application process and/or one or moredata fields that are optional for the first business applicationprocess.
 14. The computer readable medium of claim 1, wherein the firstset of selection context metadata specifies a results record, whereinthe results record is a target for output from the first businessapplication process.
 15. The computer readable medium of claim 14,wherein the first set of selection context metadata defines a mappingbetween one or more data fields in the data source and one or morefields in the results record.
 16. The computer readable medium of claim15, wherein the first set of selection context metadata defines a dataconversion filter to apply when mapping a first data field in the datasource to a first data field in the results record.
 17. The computerreadable medium of claim 1, wherein the API comprises a plurality ofmethods that must be implemented in an application class adapter for thefirst selection tool.
 18. The computer readable medium of claim 17,wherein the plurality of methods comprises a method that outputs dataselected by the first selection tool to a database table.
 19. Thecomputer readable medium of claim 17, wherein the plurality of methodscomprises a method that outputs data selected by the first selectiontool to a set of data rows.
 20. The computer readable medium of claim17, wherein the plurality of methods comprises a method that outputsdata selected by the first selection tool to one or more hypertextmarkup language (“HTML”) files that can be displayed for a user with aweb browser.
 21. The computer readable medium of claim 17, wherein theplurality of methods comprises a method that validates a selectioncriteria provided to the first selection tool by the populationselection engine.
 22. The computer readable medium of claim 17, whereinthe plurality of methods comprises a method that launches the firstselection tool.
 23. The computer readable medium of claim 17, whereinthe plurality of methods comprises a method that validates an accesslevel of a user attempting to use the first selection tool.
 24. A methodof selecting data to be processed with a business application, themethod comprising: providing, at a computer system, a populationselection framework, the population selection framework comprising: apopulation selection engine configured to provide a set of data,selected from a data source, to a business application for processing; afirst container for storing one or more sets of selection tool metadata;a second container for storing one or more sets of selection contextmetadata; and an application programming interface (“API”) for providingcommunication between the population selection engine and the one ormore selection tools; providing a user interface from the computersystem; receiving, via the user interface, a first set of selection toolmetadata for a first selection tool that can be used by the populationselection engine for selecting data to provide to the businessapplication; receiving, via the user interface, a first set of selectioncontext metadata comprising information about first a businessapplication process implemented by the business application to processthe data; configuring the population selection engine based on the firstset of selection tool metadata and the first set of selection contextmetadata; and providing, via the user interface, a display to allow theuser to select the first selection tool, for selecting a set of datafrom a data source, and the first business application process, forprocessing the selected set of data.
 25. A computer system, comprising:one or more processors; and a computer readable medium in communicationwith the one or more processors, the computer readable medium havingencoded thereon a set of instructions executable by the one or moreprocessors to implement a framework for selecting a set of data to beprocessed by a business application, the framework comprising: apopulation selection engine configured to provide a set of data,selected from a data source, to a business application for processing;one or more sets of selection tool metadata, including a first set ofselection tool metadata comprising information about first a selectiontool that can be used by the population selection engine for selectingdata to provide to the business application; one or more sets ofselection context metadata, including a first set of selection contextmetadata comprising information about first a business applicationprocess implemented by the business application to process the set ofdata; and an application programming interface (“API”) for providingcommunication between the population selection engine and the one ormore selection tools.
 26. A method of processing data with a businessapplication, the method comprising: providing, at a computer system, apopulation selection framework, the population selection frameworkcomprising: a population selection engine configured to provide a set ofdata, selected from a data source, to a business application forprocessing; one or more sets of selection tool metadata, including afirst set of selection tool metadata comprising information about firsta selection tool that can be used by the population selection engine forselecting data to provide to the business application; one or more setsof selection context metadata, including a first set of selectioncontext metadata comprising information about first a businessapplication process implemented by the business application to processthe set of data; and an application programming interface (“API”) forproviding communication between the population selection engine and theone or more selection tools; providing, from the computer system, a userinterface for a user to interact with the population selection engine;receiving, via the user interface, identification of the first businessapplication process to be used for processing the data; receiving, viathe user interface, identification of the first selection tool to beused to select data to be processed; identifying a data sourcecomprising the data to be processed with the business application;invoking, based on the first set of selection context metadata and thefirst set of selection tool metadata, the selection tool from thepopulation selection engine to select data to be processed with thebusiness application; receiving, from the selection tool, a selection ofone or more sets of data to be processed with the business applicationprocess; processing each of the one or more sets of data with thebusiness application process; and displaying an indication of a resultof the processing.